Deprecates non-inclusive config names #1467
Merged
+151
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds deprecation functionality that uses new name without replacing old
Deprecates but not changes
opensearch.requestHeadersWhitelist
Deprecates but not changes
server.xsrf.whitelist
Deprecates but not changes
server.compression.referrerWhitelist
Currently, this change is allowing the user to use
allowlist
version of the config names but under the hood, we're mapping the new value back to the old value used in code so that we don't have breaking changes for plugins. If the old non-inclusive config is used, a deprecation warning will be logged.Signed-off-by: Bishoy Boktor boktorbb@amazon.com
Description
[Describe what this change achieves]
Issues Resolved
[List any issues this PR will resolve]
Check List
yarn test:jest
yarn test:jest_integration
yarn test:ftr